implemented probability setting for bank account matching #310
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current situation
When a transaction is matched by bank account this contact gets a probability of 100%. Meaning that in some matchers the transaction is matched with 100% certainity to this contact.
Sometimes this is not the desired situation.
For example in an organization where membership are stored on the household the individual might pay for the membership and as soon as the bank account is stored at the person level all other 'magic' disappears for identifying the household and the payment is recorded at the individual with 100% certainty and therefor the matcher is executed automatically.
Proposed solution
A setting where we can set the percentage for probability for bank account matching. In the above use case I am then able to lower the certainty so that automatic execution of those matches is prevented.
The setting is defaulted to 1.0 so when updating banking the current behavior is left as it is.
See below the screenshots of the setting screen and the matching screen